<html>
<body>
Reports SLF4J, Log4j2 and akka.event.LoggingAdapter logging calls, such as <code>logger.info("{}: {}", key)</code> where the number of
<code>{}</code> placeholders
in the logger message doesn't match the number of other arguments to the logging call.
<!-- tooltip end -->
<p>
  Use the inspection option to specify which implementation SLF4J uses.
  If <strong>Check automatically</strong> is chosen, then <code>org.apache.logging.slf4j.Log4jLogger</code> is searched in the classpath.
  If this file is founded or <strong>Yes</strong> is chosen, then cases, when the last parameter with an exception type has a placeholder,
  will not be reported for SLFJ4 API.<br/>
For example:
<pre><code lang="java">
//this case will not be reported with "Yes" option
log.error("For id {}: {}", "1", new RuntimeException());
</code></pre>
In this case 'new RuntimeException()' will be printed using 'toString()', (its stacktrace will not be printed):
<pre><code lang="text">
For id 1: java.lang.RuntimeException
</code></pre>

Otherwise, it will be highlighted because the last placeholder is not used:
<pre><code lang="text">
For id 1: {}
java.lang.RuntimeException: null
</code></pre>

<strong>No</strong> option can be used to always highlight such cases when a placeholder is used for an exception
even if <code>org.apache.logging.slf4j.Log4jLogger</code> is used as a backend.<br/>

This option works only for SLF4J.
<p>
</body>
</html>